Pairing a target device with a source device and pairing the target device with a partner device

ABSTRACT

Processes, methods, systems, and devices are disclosed for pairing a target device with a source device and pairing the target device with a partner device. A user may choose between using the target device and the partner device without actively connecting the partner device to the source device. The target device and the partner device may each be a specialized device providing certain functions. For example, the source device may be a computing device, such as a smart phone or a tablet computer. The target device may be a sound bar dedicated for playing high definition surround sound that outperforms internal speakers of the source device. And the partner device may be a noise-canceling headset. The user may want to seamlessly switch between playing sounds on the sound bard and the headset from time to time under different circumstances, without needing to manually pair the headset to the computing device.

FIELD

Aspects of the disclosure generally relate to wireless communication,and more specifically to a Bluetooth communication between devices.

BACKGROUND

Specialized devices are used to playback audio (and other media) contentfor particular functions. For example, although integrated devices suchas smart phones, tablet computers, laptop computers, or televisions haveinternal speakers of their own, due to privacy, sound quality, and otherreasons, separate dedicated speakers may be used along with theintegrated devices. A user may use ear buds to avoid disturbing othersor to protect privacy. A user may use a sound bar or multiple surroundsound speakers to achieve theatrical sound effects. A user may use asmart speaker that recognizes voice input to interact with onlinecontent. A user may use a portable (e.g., battery powered) speaker toplay sound in a different environment, such as outdoor, or in a separateroom.

Very often, the integrated device may be wirelessly connected to one ofsuch specialized devices, such as when connected to a common wirelessnetwork as the integrated device or when paired with the integrateddevice via a nearfield communication network, such as Bluetooth.Bluetooth is a wireless communication technology standard for exchangingdata between fixed or mobile devices over short distances. In order touse the Bluetooth protocol, a device is often compatible with the subsetof Bluetooth profiles (often called services) necessary to use thedesired services. A Bluetooth profile is a specification regarding anaspect of Bluetooth-based wireless communication between devices.

Because specialized devices offer niche features, when a user wants tochange to a different specialized device, for example for a differentniche feature, a new connection is needed. Setting up this newconnection may be time-consuming, troublesome, and discouraging.Accordingly, methods for a smooth transition between two or morespecialized devices, as well as apparatuses and systems configured toimplement these methods are desired.

SUMMARY

All examples and features mentioned herein can be combined in anytechnically possible manner.

Aspects of the present disclosure provide a method performed by a targetdevice for establishing wireless communications with other devices. Themethod includes receiving, at the target device, a user input to enter apreparation mode. The method includes presenting, to a source device,that the target device is a discoverable device in the preparation mode,wherein the source device is operable to pair with the target device forwireless communications. The method includes scanning, by the targetdevice, for a partner device. Upon detecting at least one partnerdevice, the target device initiates a near-field communication networkand pairs with the at least one partner device in the near-fieldcommunication network.

In aspects, the scanning by the target device for the partner deviceincludes performing the scanning according to Bluetooth Low Energyprotocols.

In aspects, the user input is associated with a movement of the user.For example, the movement of the user may contact the target device,such as for providing an input by activating a control button, byvibration, or by other tactile interactions. In some cases, the user mayprovide the input via non-contact methods, such as by using a gesture onan image sensor, changing light on a light sensor, or changing motion onan infrared sensor. In some cases, the user may provide the input via aremote control. In some cases, the user may provide the input via thesource device that is already paired with the target device.

In aspects, the partner device is configured to enter a discoverablemode to be scanned by the target device. The partner device may enterthe discoverable mode in response to a similar user input, such as aninput associated with a movement of the user. Similar to the interactionwith the target device, the movement of the user may contact the partnerdevice, such as for providing an input by activating a control button,by vibration, or by other tactile interactions. In some cases, the usermay provide the input via non-contact methods, such as by using agesture on an image sensor, changing light on a light sensor, orchanging motion on an infrared sensor. In some cases, the user mayprovide the input via a remote control. In some cases, the user mayprovide the input via the source device that is already paired with thepartner device.

In aspects, the target device terminates the scanning when no partnerdevice is detected within a timeout period. For example, the timeoutperiod may be one minute, five minutes, or any preconfigured duration.

In aspects, upon detecting two or more partner devices, the targetdevice determines which one or more of the two or more partner devicesis to be paired, based on properties of the two or more partner devicesprovided to the target device during the detection. For example, theproperties of the two or more partner devices include functionalitiesassociated with sound playing or sound sampling. When the target deviceis a surround sound speaker, and the target device has detected twopartner devices, one being a noise-cancelling headset, the other being amicrophone, the target device may be paired with the noise-cancellingheadset base on similar sound playback functionalities. In some cases,the target device may use distance indicators, such as received signalstrength indicator (RSSI) normalized with antenna gains of known partnerdevices for determining relative distances of two or more partnerdevices. The target device may then choose to pair with one that has theclosest distance.

In aspects, pairing with the at least one partner device in thenear-field communication network includes transmitting informationreceived from the source device when the target device and the sourcedevice are paired. For example, the information transmitted may includedata the target device received from the source device, such as when thesource device provides data source for playing back at the target deviceand/or the partner device. In some cases, the target device and thesource device have previously been paired prior to the target deviceentering the preparation mode.

In aspects, the target device ceases to be in a discoverable state upondetecting the at least one partner device, and becomes an initiatoroperable to pair with the at least one partner device. For example,prior to detecting the at least one partner device, the target devicemay be in a pairing mode, discoverable mode, or an acceptor mode, suchas according to the classic Bluetooth protocols. The target device mayscan for a partner device according to Bluetooth Low Energy protocols inparallel to being in the pairing mode of the classic Bluetoothprotocols. Once having detected the at least one partner device, thetarget device switches into an initiator mode, in order to establish aconnection with the at least one partner device.

Aspects of the present disclosure provide a method performed by a userdevice for establishing wireless communications between at least twodevices. The method generally includes running, on the user device, amonitoring application configured to monitor a connection status betweenthe user device and a first device. The method includes identifying, bythe user device, a second device available to be connected with thefirst device in a near-field communication network. The method furtherincludes notifying a user regarding the second device and associatedavailability for connection with the first device, and providing, basedon a response of the user to the notification, at least one feedbackinstruction to the first device regarding the availability forconnection of the second device.

In aspects, the user device monitors a received signal strengthindicator (RSSI) reported by the first device and notifies the user whenthe RSSI reported drops below a threshold value.

In aspects, the user device identifies the second device by receiving,from the first device, a detection report by the first device of thesecond device. For example, the first device may scan for the seconddevice absent user input. In some cases, the first device may scan forthe second device using Bluetooth Low Energy protocols.

In aspects, the user device provides, upon receiving an approvalresponse from the user, a number of options regarding a timeout periodfor the connection between the first device and the second device foruser selection. In some cases, the number of options includes apermanent pairing option.

In aspects, the second device is triggered by the user to be availableto be connected with the first device.

In aspects, the user device plays media content on the second deviceafter the first device has been connected with the second device.

Two or more features described in this disclosure, including thosedescribed in this summary section, may be combined to formimplementations not specifically described herein.

The details of one or more implementations are set forth in theaccompanying drawings and the description below. Other features,objects, and advantages will be apparent from the description anddrawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example system in which aspects of the presentdisclosure may be implemented.

FIG. 2 illustrates an example pairing workflow without an applicationinterface, in accordance with certain aspects of the present disclosure.

FIG. 3 illustrates an example pairing workflow with an applicationinterface, in accordance with certain aspects of the present disclosure.

FIG. 4 is a flow diagram illustrating example operations that may beperformed by a target device, in accordance with certain aspects of thepresent disclosure.

FIG. 5 is a flow diagram illustrating example operations that may beperformed by a user device, in accordance with certain aspects of thepresent disclosure.

Like numerals indicate like elements.

DETAILED DESCRIPTION

The present disclosure provides processes, methods, systems, and devicesfor pairing a target device with a source device and pairing the targetdevice with a partner device. This way, a user may choose between usingthe target device and the partner device without actively connecting thepartner device to the source device. The target device and the partnerdevice may each be a specialized device providing certain functions. Forexample, the source device may be a computing device, such as a smartphone or a tablet computer. The target device may be a sound bardedicated for playing high definition surround sound that outperformsinternal speakers of the source device. In an example, the partnerdevice may be a noise-canceling headset. The user may want to seamlesslyswitch between playing sounds on the sound bar and the headset from timeto time under different circumstances, without wanting to manually pairthe headset to the computing device.

In an example, the target device may be paired with the source devicevia a nearfield communication network. The target device may scan for apartner device. Upon detecting at least one partner device, the targetdevice may initiate another nearfield communication network to pair withthe at least one partner device. In some cases, scanning for the partnerdevice may be triggered by receiving an input from a user to enter apreparation mode. Upon entering the preparation mode, the target devicemay present itself in a discoverable state to enable the source device(or another source device) to pair with the target device in thenearfield communication network. In this way, the target device mayswitch between, or simultaneously behave as, an acceptor to the sourcedevice and an initiator to the partner device. The target device mayrelay signals received from the source device to the partner device,allowing the user to use the partner device instead of the targetdevice.

In aspects, the user may use a user's device with a software application(“application”) executed thereon to interact with the target device andthe partner device. For example, a monitoring application may be runningin the user device for monitoring a connection status between the userdevice and the first device. The user device may identify one or morepartner devices available to be connected with the target device in anear-field communication network. The user device notifies the userregarding the one or more partner devices and associated availabilityfor connection with the target device. The user device then provides,based on a response to the notification, at least one feedbackinstruction to the target device regarding the availability forconnection of the second device.

The present disclosure provides benefits of establishing near-fieldcommunications among capable devices with minimal user input. Veryoften, users may find configuring devices for wireless communicationstedious and troublesome. In existing practices, establishing newconnections, though beneficial, may seemingly consume too much time oreffort. The disclosed systems and methods enable the user to activatemultiple devices with a single input (e.g., per device) or a singleaction configuration on the monitoring application. By allowing a targetdevice to switch from one role (i.e., an acceptor) to another (i.e., aninitiator), the pairing operations in near-field network can beperformed without much user involvement. The simplification of thepairing procedure may encourage the user to identify and use a mostsuitable device for particular functions.

FIG. 1 illustrates an example system 100 in which aspects of the presentdisclosure are practiced. As shown, system 100 includes a target device110 (two examples for the target device 110 are illustrated, including asound bar and a smart speaker) communicatively coupled with a sourcedevice 120 (e.g., a computing device or user device, such as asmartphone, tablet computer, or the like). One or more partner devices112 (two examples for the partner device 112 are illustrated, includinga portable speaker and a headset) may be available to accept pairingrequests from the target device 110 or the source device 120. The targetdevice 110 may be paired with the source device and receive content datafrom the source device. The partner device 112 may be a battery poweredportable device suitable for mobile or privacy applications, such as foroutdoor or Do-Not-Disturb situations.

Although the target device 110 and the one or more partner devices 112may both be capable of being directly paired with the source device 120in a near-field network environment, such pairing often requires activeuser involvement. For example, a user would be required to search foravailable devices on the source device 120 and assign specific pairingfunctions (e.g., phone calls, music playback, etc.) to specificavailable devices. Multiple steps are needed to pair available devicesto the source device, including the steps needed to prepare theavailable devices for connection to the source device. Further, thepairing procedure takes time, often minutes (due to delay in hardwareresponses, such as for obtaining pairing confirmations). The time andeffort may prevent a user from attempting to switch between the targetdevices 110 and partner devices 112 even though specific functions couldbe utilized by switching between available devices.

The present disclosure streamlines the procedure for the user toeffortlessly use any one of the target device(s) 110 and/or partnerdevices 112 with minimal time delay (i.e., no waiting time due tohardware response delay). For example, a user may only need to initiate,by performing one activation indication, a partner device 112 for thepartner device 112 to automatically pair with the target device 110 andreceive content data from the source device 120. To perform the singleactivation indication, the user may press on a hardware button on thepartner device 112, press on a hardware button on a remote of thepartner device 112 or the target device 110, or accept a notification onthe source device 120, such as via an application interface.

The target device 110 and the partner device 112 may respectivelyfurther include hardware and circuitry including processor(s)/processingsystem and memory configured to implement one or more sound managementcapabilities or other capabilities including, but not limited to, noisecancelling circuitry (not shown) and/or noise masking circuitry (notshown), body movement detecting devices/sensors and circuitry (e.g., oneor more accelerometers, one or more gyroscopes, one or moremagnetometers, etc.), geolocation circuitry and other sound processingcircuitry.

In an aspect, the target device 110 is wirelessly connected to thesource device 120 using one or more wireless communication methodsincluding, but not limited to, Bluetooth, Wi-Fi, Bluetooth Low Energy(BLE), other RF-based techniques, or the like. In an aspect, the targetdevice 110 includes a transceiver that transmits and receives data viaone or more antennae in order to exchange audio data and otherinformation with the source device 120.

In an aspect, the target device 110 includes communication circuitrycapable of transmitting and receiving audio data and other informationfrom the source device 120. The target device 110 also includes anincoming audio buffer, such as a render buffer, that buffers at least aportion of an incoming audio signal (e.g., audio packets) in order toallow time for retransmissions of any missed or dropped data packetsfrom the source device 120. For example, when the target device 110receives Bluetooth transmissions from the source device 120, thecommunication circuitry typically buffers at least a portion of theincoming audio data in the render buffer before the audio is actuallyrendered and output as audio to at least one of the transducers (e.g.,audio speakers) of the target device 110. This is done to ensure thateven if there are RF collisions that cause audio packets to be lostduring transmission, that there is time for the lost audio packets to beretransmitted by the source device 120 before they have to be renderedby the target device 110 for output by one or more acoustic transducersof the target device 110.

One example of the partner device 112 is shown as noise-cancelingheadphones; however, the techniques described herein apply to otherwireless audio devices, such as wearable audio devices, including anyaudio output device that fits around, on, in, or near an ear (includingopen-ear audio devices worn on the head or shoulders of a user) or otherbody parts of a user, such as head or neck. The partner device 112 maytake any form, wearable or otherwise, including standalone alone devices(including automobile speaker system), stationary devices (includingportable devices, such as battery powered portable speakers),headphones, earphones, earpieces, headsets, goggles, headbands, earbuds,armbands, sport headphones, neckband, or eyeglasses.

In an aspect, the target device 110 is connected to the source device120 using a wired connection, with or without a corresponding wirelessconnection. The source device 120 can be a smartphone, a tabletcomputer, a laptop computer, a digital camera, or other user device thatconnects with the target device 110. As shown, the source device 120 canbe connected to a network 130 (e.g., the Internet) and can access one ormore services over the network. As shown, these services can include oneor more cloud services 140.

In an aspect, the source device 120 can access a cloud server in thecloud 140 over the network 130 using a mobile web browser or a localsoftware application or “app” executed on the source device 120. In anaspect, the software application or “app” is a local application that isinstalled and runs locally on the source device 120. In an aspect, acloud server accessible on the cloud 140 includes one or more cloudapplications that are run on the cloud server. The cloud application canbe accessed and run by the source device 120. For example, the cloudapplication can generate web pages that are rendered by the mobile webbrowser on the source device 120. In an aspect, a mobile softwareapplication installed on the source device 120 or a cloud applicationinstalled on a cloud server, individually or in combination, may be usedto implement the techniques for low latency Bluetooth communicationbetween the source device 120 and the target device 110 in accordancewith aspects of the present disclosure. In an aspect, examples of thelocal software application and the cloud application include a gamingapplication, an audio AR application, and/or a gaming application withaudio AR capabilities. The source device 120 may receive signals (e.g.,data and controls) from the target device 110 and send signals to thetarget device 110.

An example target device 110 or the partner device 112 may includecomponents (not shown in FIG. 1 ) described below. For example, thetarget device 110 or the partner device 112 may each include one or moreprocessors, memory modules, communication modules, and/or inputinterfaces for receiving user input. The target device 110 or thepartner device 112 may each include one or more electro-acoustictransducers (or speakers) for outputting audio. The target device 110also includes a user input interface. The user input interface caninclude a plurality of preset indicators, which can be hardware buttons.The preset indicators can provide the user with easy, one press accessto entities assigned to those buttons. The assigned entities can beassociated with different ones of the digital audio sources such that asingle target device 110 can provide for single press access to variousdifferent digital audio sources.

The target device 110 or the partner device 112 may inherently includean acoustic driver or speaker to transduce audio signals to acousticenergy through the audio hardware. The target device 110 also includes anetwork interface, at least one processor, audio hardware, powersupplies for powering the various components of the target device 110,and memory. In an aspect, the processor, the network interface, thepower supplies, and the memory are interconnected using various buses,and several of the components can be mounted on a common motherboard orin other manners as appropriate. In some cases, the target device 110 orthe partner device 112 may include an enclosure that houses an optionalgraphical interface (e.g., an OLED display) which can provide the userwith information regarding currently playing (“Now Playing”) music.

A network interface may provide communication between the target device110 and other electronic user devices, such as the source device 120 andthe partner device 112, via one or more communications protocols, suchas Bluetooth classic protocol, Bluetooth low energy protocol, andothers. In general, the network interface provides either or both of awireless network interface and a wired interface (optional). Thewireless interface allows the target device 110 to communicatewirelessly with other devices in accordance with a wirelesscommunication protocol such as IEEE 802.11. The wired interface providesnetwork interface functions via a wired (e.g., Ethernet) connection forreliability and fast transfer rate, for example, used when the targetdevice 110 is not worn by a user.

In certain aspects, the network interface includes a network mediaprocessor for supporting Apple AirPlay® and/or Apple Airplay® 2. Forexample, if a user connects an AirPlay® or Apple Airplay® 2 enableddevice, such as an iPhone or iPad device, to the network, the user canthen stream music to the network connected audio playback devices viaApple AirPlay® or Apple Airplay® 2. Notably, the audio playback devicecan support audio-streaming via AirPlay®, Apple Airplay® 2 and/or DLNA'sUPnP protocols, and all integrated within one device.

All other digital audio received as part of network packets may passstraight from the network media processor through a USB bridge (notshown) to the processor and runs into the decoders, DSP, and eventuallyis played back (rendered) via the electro-acoustic transducer(s).

The network interface can further include a Bluetooth circuitry forBluetooth applications (e.g., for wireless communication with aBluetooth enabled audio source such as a smartphone or tablet) or otherBluetooth enabled speaker packages. In some aspects, the Bluetoothcircuitry may be the primary network interface due to energyconstraints. For example, the network interface may use the Bluetoothcircuitry solely for mobile applications when the target device 110 orthe partner device 112 adopts any wearable form. For example, BLEtechnologies may be used in the target device 110 or the partner device112 to extend battery life, reduce package weight, and provide highquality performance without other backup or alternative networkinterfaces.

In an aspect, the network interface supports communication with otherdevices using multiple communication protocols simultaneously at onetime. For instance, the target device 110 can support Wi-Fi/Bluetoothcoexistence and can support simultaneous communication using both Wi-Fiand Bluetooth protocols at one time. For example, the target device 110can receive an audio stream from a smart phone using Bluetooth and canfurther simultaneously redistribute the audio stream to one or moreother devices over Wi-Fi. In an aspect, the network interface mayinclude only one RF chain capable of communicating using only onecommunication method (e.g., Wi-Fi or Bluetooth) at one time. In thiscontext, the network interface may simultaneously support Wi-Fi andBluetooth communications by time-sharing the single RF chain betweenWi-Fi and Bluetooth, for example, according to a time divisionmultiplexing (TDM) pattern.

Streamed data may pass from the network interface to the processor. Theprocessor can execute instructions (e.g., for performing, among otherthings, digital signal processing, decoding, and equalizationfunctions), including instructions stored in the memory. The processorcan be implemented as a chipset of chips that includes separate andmultiple analog and digital processors. The processor can provide, forexample, for coordination of other components of the audio target device110, such as control of user interfaces.

A memory may store software/firmware related to protocols and versionsthereof used by the target device 110 or the partner device 112 forcommunicating with other networked devices, including the source device120. For example, the software/firmware governs how the target device110 communicates with other devices for synchronized playback of audio.In an aspect, the software/firmware includes lower level frame protocolsrelated to control path management and audio path management. Theprotocols related to control path management generally include protocolsused for exchanging messages between speakers. The protocols related toaudio path management generally include protocols used for clocksynchronization, audio distribution/frame synchronization, audiodecoder/time alignment, and playback of an audio stream. In an aspect,the memory can also store various codecs supported by the speakerpackage for audio playback of respective media formats. In an aspect,the software/firmware stored in the memory can be accessible andexecutable by the processor for synchronized playback of audio withother networked speaker packages.

In aspects, the protocols stored in the memory may include BLE accordingto, for example, the Bluetooth Core Specification Version 5.2 (BT5.2).The target device 110 or the partner device 112, and the variouscomponents therein, are provided herein to sufficiently comply with orperform aspects of the protocols and the associated specifications. Forexample, BT5.2 includes enhanced attribute protocol (EATT) that supportsconcurrent transactions. A new L2CAP mode is defined to support EATT. Assuch, the target device 110 includes hardware and software componentssufficiently to support the specifications and modes of operations ofBT5.2, even if not expressly illustrated or discussed in thisdisclosure. For example, the target device 110 may utilize LEIsochronous Channels specified in BT5.2.

The processor may provide a processed digital audio signal to the audiohardware which includes one or more digital-to-analog (D/A) convertersfor converting the digital audio signal to an analog audio signal. Theaudio hardware also includes one or more amplifiers which provideamplified analog audio signals to the electroacoustic transducer(s) forsound output. In addition, the audio hardware can include circuitry forprocessing analog input signals to provide digital audio signals forsharing with other devices, for example, other speaker packages forsynchronized output of the digital audio.

The memory can include, for example, any non-transitory memory such asflash memory and/or non-volatile random access memory (NVRAM). In someaspects, instructions (e.g., software) are stored in an informationcarrier. The instructions, when executed by one or more processingdevices (e.g., the processor), perform one or more processes, such asthose described elsewhere herein. The instructions can also be stored byone or more storage devices, such as one or more computer ormachine-readable mediums (for example, the memory, or memory on theprocessor). The instructions can include instructions for performingdecoding (i.e., the software modules include the audio codecs fordecoding the digital audio streams), as well as digital signalprocessing and equalization.

Example Pairing and Mode Switch Without User Application Input

Aspects of the present disclosure provide techniques for pairing, at atarget device with a partner device. In one example, the target devicereceives user input to enter a preparation mode. The target device maypresent to a source device that the target device is a discoverabledevice (e.g., in a discoverable mode) upon entering the preparationmode. In addition, the target device scans for a partner device, if any.Upon detecting at least one partner device, the target device may pairwith the detected at least one partner device via a near-fieldcommunication network, such as a Bluetooth network.

FIG. 2 illustrates an example pairing workflow without an applicationinterface, in accordance with certain aspects of the present disclosure.As shown, the target device 110, illustrated as a sound bar, may becontrolled via a remote controller 210. A user may activate thepreparation mode in the target device 110 by pressing the preparationmode button 205 on the remote controller 210. In response, the targetdevice 110 enters the preparation mode (e.g., pairing mode) at 220. Insome cases, when the target device 110 is in the preparation mode, thetarget device 110 may use two or more different wireless protocols. Forexample, the target device 110 may behave as a passive discoverabledevice according to Bluetooth classic protocols and behave as aninitiator when scanning for a partner device 112 according to Bluetoothlow energy protocols. Upon detecting a partner device 112, the targetdevice 110 may role-switch to become an initiator at 240, according toBluetooth classic protocols. The target device 110 may then pair withthe partner device 112 at 250.

In aspects, for power saving reasons, the partner device 112 may notalways be discoverable by the target device 110. In some cases, a usermay activate the partner device 112 to enter a pairing mode by pressingthe button 203 on the partner device 112. Upon activation, the partnerdevice 112 may be in pairing mode at 230, according to at least one ofBluetooth classic or Bluetooth low energy protocols. At 250, the partnerdevice 112 may behave as an acceptor to pair with the target device 250.In aspects, the partner device 112 may stay in the pairing mode wheneverthe partner device 112 is powered on, such that the user need notseparately activate the pairing mode for the partner device 112.

In aspects, upon pairing with the target device 110, the partner device112 may playback data signals received from the target device 110. Forexample, the partner device 112 may play audio together with, or in theplace of, the target device 110.

Example Pairing and Mode Switch With User Application Input

Aspects of the present disclosure provide techniques for a user device,such as the source device 120 of FIG. 1 , to establish wirelesscommunication between at least two devices, such as the target device110 and the partner device 112 of FIG. 1 . In one example, the userdevice runs a monitoring application configured to monitor a connectionstatus between the user device and a first device, such as the targetdevice 110. The user device identifies a second device available to beconnected with the first device in a near-field communication network.For example, the user device may identify a partner device 112 of FIG. 1via the target device 110, such as when the target device 110 scans anddetects the partner device 112.

Upon identifying the second device, the user device notifies the userregarding the second device and the associated availability forconnection with the first device. For example, the user may receive apush notification in the monitoring application of the user device. Thepush notification may include one or more second devices available forconnection with the first device. The user device, after receiving aresponse from the user, provides at least one feedback instruction tothe first device regarding the availability for connection of the seconddevice. For example, the feedback instruction may indicate the firstdevice is to connect with the second device in the near-fieldcommunication network.

FIG. 3 illustrates an example pairing workflow with an applicationinterface, in accordance with certain aspects of the present disclosure.As shown, the target device 110 may be connected with and report to theuser device 320 via a near-field network 310. The user device 320 runs amonitoring application as well as other applications that may playbackmultimedia content on the target device 110. The user device 320 mayrepresent a single device or a group of user devices 320 that allow auser to install the monitoring application therein. During operation, at340, the partner device 112 enters into a pairing mode and is detectedby the target device 110. The detection is monitored by the user device320 via the connection between the target device 110 and the user device320 via the network 310. At 330, the target device 110 becomes aninitiator for pairing with the partner device 112. For example, themonitoring application on the user device 320 may notify the userregarding the availability of the partner device 112 and allows the userto choose whether or not to connect to the partner device 112. Uponreceiving an affirmative response from the user, the target device 110pairs with the partner device, such as according to Bluetooth classicprotocols.

In some cases, the user may select a pairing duration for the targetdevice 110 and the partner device 112, such that the pairing may expireafter a period of time. The period of time may include preset durationsin terms of hours (e.g., 1, 2, 4 hours) or may be set to indefiniteuntil cancellation. In some cases, the selection of the pairing durationand the approval or indication for the pairing procedure by the user maybe the same action. For example, when the user selects a specificpairing duration and confirms, such action approves the pairingoperations between the target device 110 and the partner device 112.

Methods and Processes for Pairing and Mode Switch

FIG. 4 is a flow diagram illustrating example operations 400 that may beperformed by a target device for establishing wireless communicationswith other devices. For example, the example operations 400 may beperformed by the target device 110 of FIG. 1 .

The example operations 400 begin, at 402, receiving, at the targetdevice, a user input to enter a preparation mode. At 404, the targetdevice presents to a source device that the target device is adiscoverable device in the preparation mode, wherein the source deviceis operable to pair with the target device for wireless communications.At 406, the target device scans for a partner device. Upon detecting atleast one partner device, the target device initiates, at 408, anear-field communication network. At 410, the target device pairs withthe partner device in the near-field communication network.

In aspects, the target device may scan for the partner device byperforming the scanning according to Bluetooth Low Energy protocols.

In aspects, the user input is associated with a movement of the user.For example, the movement of the user contacts the target device, suchas pressing a control button on the target device. In some cases, theuser input may be provided to the target device without physicalcontact, such as by detecting the movement via a motion sensor, such asan infrared sensor, an accelerator, an inertia-measurement-unit, or thelike. In some cases, the user input may be provided via a remotecontrol, such as the remote control 210 of FIG. 2 .

In aspects, the partner device may be configured to enter a discoverablemode (or discoverable state) to be scanned by the target device. Forexample, similar to the target device receiving the user input, thepartner device may also receive a user input associated with a movementof the user to enter the discoverable mode.

In aspects, the target device may terminate the scanning by the targetdevice when no partner device is detected within a timeout period. Forexample, the timeout period may be predefined in the internal program ofthe target device. In some cases, the timeout period may be specified bythe user.

In aspects, the target device, upon detecting two or more partnerdevices, may determine which one or more of the two or more partnerdevices to pair with, based on properties of the two or more partnerdevices provided to the target device during the detection. For example,the properties of the two of more partner devices includefunctionalities associated with sound playing or sound sampling. Thetarget device may automatically determine one of the two or more partnerdevices having similar functionalities as the target device forconnection. When the target device is a sound bar, for example, thetarget device may select other sound playback devices. On the otherhand, when the target device is a microphone, the target device mayselect another sound sampling device to assist or to replace theoperations in the target device.

In aspects, the target device may pair with the at least one partnerdevice in the near-field communication network by transmittinginformation received from the source device when the target device andthe source device are paired. For example, the target device and thesource device may have previously been paired prior to the target deviceentering the preparation mode. In some cases, the target device maymaintain the existing connection with the source device. In some cases,the target device may be discovered by another source device and receiveindication to handover the connection to the new source device.

In aspects, upon detecting the at least one partner device, the targetdevice may cease to be in a discoverable state and becomes an initiatorto pair with the at least one partner device.

FIG. 5 is a flow diagram illustrating example operations 500 that may beperformed by a user device for establishing wireless communicationsbetween at least two devices. For example, the example operations 500may be performed by the source device 120 of FIG. 1 .

The example operations 500 begin, at 502, by running, in the userdevice, a monitoring application configured to monitor a connectionstatus between the user device and a first device. At 504, the userdevice identifies a second device available to be connected with thefirst device in a near-field communication network. At 506, the userdevice notifies a user regarding the second device and associatedavailability for connection with the first device. At 508, the userdevice provides, based on a response of the user to the notification, atleast one feedback instruction to the first device regarding theavailability for connection of the second device.

In aspects, the user device may monitor a received signal strengthindicator (RSSI) reported by the first device and notifying the userwhen the RSSI reported drops below a threshold value. When the RSSIdrops below the threshold value, the user device may notify the usersuch that alternative, more reliable connection options may be used.

In aspects, the user device may identify the second device by receiving,from the first device, a detection report by the first device of thesecond device. For example, the user device may utilize scanning resultsof the first device, in addition to or in the place of, scanning for thesecond device. In some cases, the first device scans for the seconddevice absent user input. The first device may scan for the seconddevice using Bluetooth Low Energy protocols.

In aspects, the user device may further provide, upon receiving anapproval response from the user, a number of options regarding a timeoutperiod for the connection between the first device and the second devicefor user selection. For example, the number of options may include apermanent paring option.

In aspects, the second device may be triggered by the user to beavailable to be connected with the first device. For example, the seconddevice may receive a user input, according to various mannersaforementioned.

In aspects, the user device may play media content on the second deviceafter the first device has been connected with the second device. Forexample, the first device may relay content data to the second device.In some cases, the first device may enable a direct data link betweenthe user device and the second device after the connection.

In other aspects, the disclosed methods are applicable to wirelessearbuds, earhooks, or ear-to-ear devices. For example, a host like amobile phone may be connected over Bluetooth to a bud (e.g., right side)and that right-side bud further connects to the left-side bud usingeither a Bluetooth link or using other wireless technologies like NFMIor NFEMI. The left-side bud is first time-synchronized with theright-side bud. Audio frames (compressed in mono) are sent from theleft-side bud with its timestamp (which is synchronized with the rightbud's timestamp) as described in the technology above. The right budwill forward these encoded mono frames along with its own frames. Theright bud will not wait for an audio frame from the left bud with thesame timestamp. Instead, the right-bud sends whatever frame is availableand ready to be sent with suitable packing. It is the responsibility ofthe receiving application in the host to assemble the packets using thetimestamp and the channel number. The receiving application, dependingupon how it is configured, can choose to merge the decoded mono channelof one bud and a decoded mono channel of the other bud into a stereotrack based on the timestamp included in the header of the receivedencoded frames. The present disclosure allows the right-side bud tosimply forward the audio frames from the left-side bud without decodingthe frame. This helps to conserve battery power in truly wireless audiodevices.

In some aspects, the techniques variously described herein can be usedto improve virtual personal assistant (VPA) functionality. For instance,the techniques described herein can improve wake-up word (WuW) supportfor one or more VPAs (such as Google Assistant, Amazon's Alexa, Apple'sSiri, Samsung's Bixby, Microsoft's Cortana, Tencent's Xiaowei, Huawei'sCelia, and so forth). For example, in some such aspects, the techniquesdescribed herein enable offloading of WuW processing from the sourcedevice (e.g., headphones, earbuds, or some other wearable device) to thetarget device (e.g., a smartphone, tablet computer, or other device withrelatively more processing capabilities). This can provide a benefit toimplementing WuW functionality (for VPAs or other applications), as WuWprocessing may be large in size and/or use intensive computing resourcessuch that a relatively more capable processing device (such as asmartphone) can provide better support for the WuW processing. Inaddition, by offloading the WuW processing from the source device to thetarget device, enabling multiple simultaneous WuW support (e.g., for twoor more VPAs). This can benefit the user by allowing the best VPA to beused for a desired use case, either manually (e.g., by using thespecific WuW to access the desired VPA) or automatically (e.g., byhaving a single WuW that routes the VPA request to the VPA service thatcan best handle the inquiry/request). For example, a VPA request toAmazon's Alexa (manually made by saying “Alexa” or automatically madevia a custom WuW) may be used to play music while a VPA request toGoogle Assistant (manually made by saying “Hey Google” or automaticallymade via the custom WuW) may be used to schedule a calendar meeting.This can also lead to easier VPA WuW support certification, as the VPAservice's software can be run on the target device as opposed to usingthe source device's software to detect and process WuWs. Further, theWuW support can be standardized across multiple different target devicesto support multiple different source devices.

In some aspects, the techniques variously described herein can be usedto determine contextual information for a source device and/or the userof the source device. For instance, the techniques can be used to helpdetermine aspects of the user's environment (e.g., noisy location, quietlocation, indoors, outdoors, on an airplane, in a car, etc.) and/oractivity (e.g., commuting, walking, running, sitting, driving, flying,etc.). In some such aspects, various data received from the sourcedevice can be processed at the target device to determine suchcontextual information and provide new or enhanced experiences to theuser. For example, this could enable playlist or audio contentcustomization, noise cancellation adjustment, and/or other settingsadjustments (e.g., audio equalizer settings, volume settings,notification settings, etc.), to name a few examples. As source devices(e.g., headphones or earbuds) typically have limited resources (e.g.,memory and/or processing resources), using the techniques describedherein to offload the processing of data from sensors of the sourcedevice(s) to a target device while having a system to synchronize dataat the target device provides a variety of applications. In someaspects, the techniques disclosed herein enables the user device toautomatically identify an optimized or a most favorable configuration orsetting for the synchronized audio capture operations.

In some aspects, the techniques variously described herein can be usedfor a multitude of audio/video applications. For instance, thetechniques can be used for stereo or surround sound audio capture from asource device to be synchronized at a target device with video capturedfrom the same source device, another source device, and/or the targetdevice. For example, the techniques can be used to synchronize stereo orsurround sound audio captured by microphones on a pair of headphoneswith video captured from a camera on or connected to the headphones, aseparate camera, and/or the camera of a smartphone, where the smartphone(which is the target device in this example) performs thesynchronization of the audio and video. This can enable real-timeplayback of stereo or surround sound audio with video (e.g., for livestreaming), capture for recorded videos with stereo or surround soundaudio (e.g., for posting to social media platforms or news platforms).In addition, the techniques described herein can enable wirelesscaptured audio for audio or video messages without interrupting a user'smusic or audio playback. Thus, the techniques described herein enablethe ability to produce immersive and/or noise-free audio for videosusing a wireless configuration. Moreover, as can be understood based onthis disclosure, the techniques described enable schemes that were onlypreviously achievable using a wired configuration, so the techniquesdescribed free the user from the undesirable and uncomfortableexperience of being tethered by one or more wires.

It can be noted that, descriptions of aspects of the present disclosureare presented above for purposes of illustration, but aspects of thepresent disclosure are not intended to be limited to any of thedisclosed aspects. Many modifications and variations will be apparent tothose of ordinary skill in the art without departing from the scope andspirit of the described aspects.

In the preceding, reference is made to aspects presented in thisdisclosure. However, the scope of the present disclosure is not limitedto specific described aspects. Aspects of the present disclosure cantake the form of an entirely hardware aspect, an entirely softwareaspect (including firmware, resident software, micro-code, etc.) or anaspect combining software and hardware aspects that can all generally bereferred to herein as a “component,” “circuit,” “module” or “system.”Furthermore, aspects of the present disclosure can take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) can beutilized. The computer readable medium can be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium can be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples a computer readable storage medium include: anelectrical connection having one or more wires, a hard disk, a randomaccess memory (RAM), a read-only memory (ROM), an erasable programmableread-only memory (EPROM or Flash memory), an optical fiber, a portablecompact disc read-only memory (CD-ROM), an optical storage device, amagnetic storage device, or any suitable combination of the foregoing.In the current context, a computer readable storage medium can be anytangible medium that can contain, or store a program.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality and operation of possible implementations ofsystems, methods and computer program products according to variousaspects. In this regard, each block in the flowchart or block diagramscan represent a module, segment or portion of code, which comprises oneor more executable instructions for implementing the specified logicalfunction(s). In some alternative implementations the functions noted inthe block can occur out of the order noted in the figures. For example,two blocks shown in succession can, in fact, be executed substantiallyconcurrently, or the blocks can sometimes be executed in the reverseorder, depending upon the functionality involved. Each block of theblock diagrams and/or flowchart illustrations, and combinations ofblocks in the block diagrams and/or flowchart illustrations can beimplemented by special-purpose hardware-based systems that perform thespecified functions or acts, or combinations of special purpose hardwareand computer instructions.

What is claimed is:
 1. A method performed by a target device forestablishing wireless communications with other devices, the methodcomprising: receiving, at the target device, a user input to enter apreparation mode; presenting to a source device that the target deviceis a discoverable device in the preparation mode, wherein the sourcedevice is operable to pair with the target device for wirelesscommunications; scanning, by the target device, for a partner device;upon detecting at least one partner device, initiating, by the targetdevice, a near-field communication network; and pairing with the atleast one partner device in the near-field communication network.
 2. Themethod of claim 1, wherein the scanning by the target device for thepartner device comprises performing the scanning according to BluetoothLow Energy protocols.
 3. The method of claim 1, wherein the user inputis associated with a movement of the user.
 4. The method of claim 3,wherein the movement of the user contacts the target device.
 5. Themethod of claim 1, wherein the partner device is configured to enter adiscoverable mode to be scanned by the target device.
 6. The method ofclaim 1, further comprising terminating the scanning by the targetdevice when no partner device is detected within a timeout period. 7.The method of claim 1, further comprising, upon detecting two or morepartner devices, determining which one or more of the two or morepartner devices is to be paired, based on properties of the two or morepartner devices provided to the target device during the detection. 8.The method of claim 7, wherein the properties of the two of more partnerdevices include functionalities associated with sound playing or soundsampling.
 9. The method of claim 1, wherein pairing with the at leastone partner device in the near-field communication network comprisestransmitting information received from the source device when the targetdevice and the source device are paired.
 10. The method of claim 9,wherein the target device and the source device have previously beenpaired prior to the target device entering the preparation mode.
 11. Themethod of claim 1, further comprising: ceasing to be in a discoverablestate upon detecting the at least one partner device; and becoming aninitiator operable to pair with the at least one partner device.
 12. Amethod performed by a user device for establishing wirelesscommunications between at least two devices, the method comprising:running, in the user device, a monitoring application configured tomonitor a connection status between the user device and a first device;identifying, by the user device, a second device available to beconnected with the first device in a near-field communication network;notifying a user regarding the second device and associated availabilityfor connection with the first device; and providing, based on a responseof the user to the notification, at least one feedback instruction tothe first device regarding the availability for connection of the seconddevice.
 13. The method of claim 12, further comprising monitoring areceived signal strength indicator (RSSI) reported by the first deviceand notifying the user when the RSSI reported drops below a thresholdvalue.
 14. The method of claim 12, wherein identifying by the userdevice the second device comprises receiving, from the first device, adetection report by the first device of the second device.
 15. Themethod of claim 14, wherein the first device scans for the second deviceabsent user input.
 16. The method of claim 14, wherein the first devicescans for the second device using Bluetooth Low Energy protocols. 17.The method of claim 12, further comprising providing, upon receiving anapproval response from the user, a plurality of options regarding atimeout period for the connection between the first device and thesecond device for user selection.
 18. The method of claim 17, whereinthe plurality of options includes a permanent pairing option.
 19. Themethod of claim 12, wherein the second device is triggered by the userto be available to be connected with the first device.
 20. The method ofclaim 12, further comprising playing media content on the second deviceafter the first device has been connected with the second device.